From 25755ef315b1529b3c68aec577195645e30a706a Mon Sep 17 00:00:00 2001 From: "kaf24@firebug.cl.cam.ac.uk" Date: Thu, 19 May 2005 14:03:42 +0000 Subject: [PATCH] bitkeeper revision 1.1159.258.139 (428c9cbe7Sc87xp33OYAeObd7e3N3g) Do not set jumbo MTU on the fake netfront/back loopback device. It causes packet loss at the Ethernet bridge (since bridges do not fragment IP packets). Signed-off-by: Keir Fraser --- linux-2.6.11-xen-sparse/drivers/xen/netback/loopback.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/linux-2.6.11-xen-sparse/drivers/xen/netback/loopback.c b/linux-2.6.11-xen-sparse/drivers/xen/netback/loopback.c index 9dffff0fc2..ebada3721a 100644 --- a/linux-2.6.11-xen-sparse/drivers/xen/netback/loopback.c +++ b/linux-2.6.11-xen-sparse/drivers/xen/netback/loopback.c @@ -94,7 +94,15 @@ static void loopback_construct(struct net_device *dev, struct net_device *lo) dev->get_stats = loopback_get_stats; dev->tx_queue_len = 0; - dev->mtu = 16*1024; + + /* + * We do not set a jumbo MTU on the interface. Otherwise the network + * stack will try to send large packets that will get dropped by the + * Ethernet bridge (unless the physical Ethernet interface is configured + * to transfer jumbo packets). If a larger MTU is desired then the system + * administrator can specify it using the 'ifconfig' command. + */ + /*dev->mtu = 16*1024;*/ } static int __init loopback_init(void) -- 2.30.2